feat(graphql-js-tag): add document cache#631
Merged
Conversation
pavelglac
force-pushed
the
user/pavelglac/caching-documents
branch
from
c1aa33e to
db4d9d0
Compare
pavelglac
force-pushed
the
user/pavelglac/caching-documents
branch
from
db4d9d0 to
d330177
Compare
vladar
approved these changes
Feb 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In version 3.10.5 Apollo changed how hook behaves when the query reference changes. Previously, it would simply change the ref and continue. The new behavior triggers a rerender. Our GraphQL tag creates a new reference for each call, which leads to infinite rerendering.
This fix aligns with graphql-tag.